Imaging system for identifying medication containers

ABSTRACT

The imaging system includes a rotating element that is configured to rotate about a central axis. A plurality of scanners are fixedly attached with the rotating element. Each scanner has a lens that faces generally towards the central axis, and the scanners are spaced apart from one another around the central axis. The scanners are configured to identify an optically readable machine readable code contained on the medication container. An actuator is operably connected with the rotating element and is configured to rotate the rotating element and the scanners around the central axis from respective e first positions to respective second positions to allow the scanners to image different areas of the medication container in response to a failure of the scanners to identify the machine readable code when the scanners were in the respective first positions.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention is related generally to high volume fillingcenter, e.g., an automated pharmacy. More specifically, the presentinvention is related to a system in a high volume filling center whichidentifies and verifies the contents of a plurality of containers, e.g.,medication containers.

2. Related Art

A high volume pharmacy may process and fill a large number ofprescriptions and prescription orders using one or more automatedsystems. During the processing operation, it is important to verify thecontents of a medication container prior to sending that medicationcontainer to a customer using a verification system. Such a verificationoperation may involve the reading of an optical machine readable code,e.g., a bar code. However, some verification systems may have difficultydetecting and reading the machine readable code on some medicationcontainers, thereby slowing throughput in the high volume pharmacy.

SUMMARY OF THE INVENTION AND ADVANTAGES

One aspect of the present disclosure is related to an imaging system foridentifying medication containers. The imaging system includes arotating element that is configured to rotate about a central axis. Aplurality of scanners are fixedly attached with the rotating element.Each scanner has a lens that faces generally towards the central axis,and the scanners are spaced apart from one another around the centralaxis. The scanners are configured to identify an optically readablemachine readable code contained on the medication container. An actuatoris operably connected with the rotating element and is configured torotate the rotating element and the scanners around the central axisfrom respective e first positions to respective second positions toallow the scanners to image different areas of the medication containerin response to a failure of the scanners to identify the machinereadable code when the scanners were in the respective first positions.

In an example embodiment, the scanners are cameras.

In an example embodiment, the plurality of scanners includes fourscanners that are equidistantly spaced apart from one another around thecentral axis.

In an example embodiment, the actuator is a linear actuator.

In an example embodiment, the respective second positions of thescanners are no greater than thirty degrees (30°) from the respectivefirst positions of the scanners.

In an example embodiment, the scanners are cameras, and the rotatingelement includes a circular plate and a plurality of camera mount rodsthat interconnect the cameras with the rotating element.

In an example embodiment, the imaging system further includes aplurality of clamps, and each clamp attaches one of the cameras to oneof the camera mount rods.

According to another aspect of the present disclosure, a containerhandling and verification system is provided. The system includes acontainer area for storing at least two different types of medicationcontainers, each of the medication containers having an opticallyreadable machine readable code. The system further includes a pick andplace mechanism that is configured to engage a first medicationcontainer and deliver the first medication container to a location alonga central axis of the imaging system. The imaging system includes aplurality of imaging devices that face towards the central axis. Theimaging system further includes an actuator that is configured to rotatethe imaging devices about the central axis. The imaging devices areconfigured to perform a first scan on the label of the first medicationcontainer with the imaging devices for the machine readable code. Inresponse to the imaging devices not detecting the machine readable codeon the label of the first medication container, the image processingsystem being configured to activate the actuator to rotate the imagingdevices about the central axis and perform a second scan on the label ofthe first medication container.

In an example embodiment, the imaging devices are cameras.

In an example embodiment, the system further includes a controller thatis in electrical communication with and controls the pick and placemechanism, the imaging devices, and the actuator upon receiving an orderfor a medication container.

In an example embodiment, the system further includes a conveyor chute,and the pick and place mechanism is configured to drop the firstmedication container in a discharge bin in response to either nodetection of the machine readable code during both the first and secondscans or in response to the machine readable code not matching anexpected machine readable code based upon the order received by thecontroller.

In an example embodiment, the system further includes a label applicatorfor applying a new label to the first medication container.

According to another aspect of the present disclosure, a method ofverifying the contents of a medication container that has an opticallyreadable machine readable code is provided. The method includes the stepof holding a medication container in a stationary position such that aplurality of imaging devices are facing the medication container. Themethod continues with the step of conducting a first visual scan of themedication container with the imaging devices for the machine readablecode. The method proceeds with the step of, in response to the imagingdevices not detecting the machine readable code, rotating the imagingdevices around the medication container and then conducting a secondvisual scan of the medication container with the imaging devices for themachine readable code with the imaging devices being at a differentangle.

In an example embodiment, the method further includes the steps ofreceiving with a controller an order for a medication container andpicking up a first medication container of a plurality of differenttypes of medication containers with the pick and place mechanism.

In an example embodiment, in response to the imaging devices reading themachine readable code during either the first visual scan or the secondvisual scan, then the method proceeds as follows. If the machinereadable code matches an expected machine readable code based on theorder, then the method continues with placing the medication containerin a first location using the pick and place mechanism. If the machinereadable code does not match an expected machine readable code based onthe order, then the method continues with placing the medicationcontainer in a second location that is different than the first locationusing the pick and place mechanism.

In an example embodiment, the method further includes the step ofapplying a label to the medication container prior to placing themedication container in the first location.

In an example embodiment, the first location is a conveyor, and thesecond location is a discharge bin.

In an example embodiment, the imaging devices are fixedly attached to arotating element, and an actuator is configured to rotate the rotatingelement and the cameras.

In an example embodiment, the actuator is a linear actuator.

In an example embodiment, the actuator is pneumatic.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features and advantages of the invention will becomemore readily appreciated when considered in connection with thefollowing description of the presently preferred embodiments, appendedclaims and accompanying drawings, in which:

FIG. 1 is a block diagram of an example system according to an exampleembodiment;

FIG. 2 is a block diagram of an example order processing device that maybe deployed within the system of FIG. 1;

FIG. 3 is a block diagram of an example unit of use device that may bedeployed in the order processing device of FIG. 2;

FIG. 4A is a perspective view of an exemplary embodiment of an imagingsystem that may be employed in the unit of use device of FIG. 3;

FIG. 4B is another perspective view of the exemplary embodiment of theimaging system and showing the imaging system engaging a differentbottle than is shown in FIG. 4A;

FIG. 5 is a front elevation view of the imaging system of FIG. 4 andshowing a plurality of cameras in respective first positions;

FIG. 6 is another front elevation view of the imaging system of FIG. 4and showing the plurality of cameras in respective second positions thatare different than the first positions shown in FIG. 5;

FIG. 7 is a fragmentary and cross-sectional view of a portion of theimaging system of FIG. 4;

FIG. 8 is a perspective and fragmentary view of a portion of the imagingsystem of FIG. 4; and

FIG. 9 is a flow chart illustrating a method according to one aspect ofthe subject invention.

DESCRIPTION OF THE ENABLING EMBODIMENT

FIG. 1 is a block diagram of an example implementation of a system 100,according to an example embodiment. While the system 100 is generallydescribed as being deployed in a high volume pharmacy or fulfillmentcenter (e.g., a mail order pharmacy, a direct delivery pharmacy, anautomated pharmacy, multiple package delivering center, and the like),the system 100 and/or components thereof may otherwise be deployed(e.g., in a lower volume pharmacy). The system 100 can include afulfillment center that takes a manufacturer's container, relabels thecontainer and uses the relabeled container to fill an order. A highvolume pharmacy may be a pharmacy that is capable of fillingprescriptions automatically, mechanically, manually, or a combinationthereof. The system 100 may include a benefit manager device 102, apharmacy device 106, and a user device 108, which may communicate witheach other directly and/or over a network 104. The system 100 may alsoinclude a storage device 110. The system 100 can include a plurality ofdifferent containers, e.g., tens of different types of containers,hundreds of different types of containers, or multiples thereof. Thedifferent containers in the system 100 can be of different sizes andshapes and labeled with a machine readable code, which can be difficultfor the system to read due to the different shapes and sizes of thecontainers.

The benefit manager 102 is a device operated by an entity that is atleast partially responsible for creation and/or management of thepharmacy or drug benefit. While such an entity operating the benefitmanager device 102 is typically a pharmacy benefit manager (PBM), otherentities may operate the benefit manager device 102 either on behalf ofthemselves, the PBM, another entity, or other entities. For example, thebenefit manager device 102 may be operated by a health plan, a retailpharmacy chain, a drug wholesaler, a data analytics or other type ofsoftware-related company, or the like. In some embodiments, a PBM thatprovides the pharmacy benefit may also provide one or more than oneadditional benefits including a medical or health benefit, a dentalbenefit, a vision benefit, a wellness benefit, a radiology benefit, apet care benefit, an insurance benefit, a long term care benefit, anursing home benefit, and the like. The PBM may, in addition to its PBMoperations, operate one or more than one pharmacy. The pharmaceuticalvending machines or kiosks, and the like. The PBM device may track themedications in the containers stored in the system 100. The PBM devicemay not be able to track the shape of the manufacturer containerassociated with the materials stored in the container or the location ofthe machine readable code on the manufacturer container. The materialscan be medications or supplements.

Some of the operations of the PBM that operates the benefit managerdevice 102 may include the following activities and processes. A member(or a person on behalf of the member) of a pharmacy benefit planadministered by or through the PBM attempts to obtain a prescriptiondrug at a retail pharmacy location (e.g., a location of a physicalstore) from a pharmacist or a pharmacist technician. The member may alsoattempt to obtain the prescription drug through mail order drug deliveryfrom a mail order pharmacy location, which may be the high volumepharmacy system 100. In some embodiments, the member may also attempt toobtain the prescription drug directly or indirectly through the use of amachine, such as a kiosk, vending unit, mobile electronic device, or adifferent type of mechanical electrical, electronic communicationdevice, and/or computing device. Such a machine may be filled with theprescription drug in prescription packaging, which may include multipleprescription components, by the high volume pharmacy system 100.

The member may have a copayment for the prescription drug that reflectsan amount of money that the member is responsible to pay the pharmacyfor the prescription drug. The money paid by the member to the pharmacymay come from personal funds of the member, a health savings account(HAS) of the member or the member's family, a health reimbursementarrangement (HRA) of the member or the member's family, a flexiblespending account (FSA) of the member or the member's family, or thelike. In some instances, an employer of the member may directly orindirectly fund or reimburse the member for the copayments.

The amount of the co-pay required form the member may vary withdifferent pharmacy benefit plans having different plan sponsors orclients and/or prescription drugs. The member's copayment may be basedon a flat copayment (e.g., $10), co-insurance (e.g., 10%), and/or adeductible (e.g., for first $500 of annual prescription drug expenses)for certain prescription drugs, certain types and/or classes ofprescription drugs, and/or all prescription drugs. The copayment may bestored in the storage 110 or determined by the benefit manager device102.

In some instances, the member may not pay the copayment or may only paya portion of the copayment for the prescription drug. For example, ifthe usual and customary cost for a generic version of a prescriptiondrug is $4, and the member's flat copayment is $20 for the prescriptiondrug, the member may only be required to pay $4 to receive theprescription drug. In another example involving a worker's compensationclaim. No copayment may be due by the member for the prescription drug.

In addition, copayments may also vary based on different deliverychannels used for the prescription drug to be received by the member.For example, the copayment for receiving the prescription drug from amail order pharmacy location may be less than the copayment forreceiving the prescription drug from a retail pharmacy location.

In conjunction with receiving the copayment (if any) from the member anddispensing the prescription drug to the member, the pharmacy submits aclaim to the PBM for the prescription drug. After receiving the PBM(e.g., through the benefit manager device 102) may perform certainadjudication operations including verifying eligibility of the member,identifying and/or reviewing an applicable formulary for the member todetermine any appropriate copayment, coinsurance, and deductible for theprescription drug, and performing a drug utilization review (DUR) on themember. The PBM provides a response to the pharmacy (e.g., from thebenefit manager device 102 to the pharmacy device 106) followingperformance of at least some of the aforementioned operations.

As part of the adjudication, a plan sponsor (or the PBM on behalf of theplan sponsor) ultimately reimburses the pharmacy for filling theprescription drug when the prescription drug was successfullyadjudicated.

The aforementioned adjudication operations generally occur before thecopayment is received and the prescription drug is dispensed. However,in some instances these operations may occur simultaneously,substantially simultaneously, or in a different order. In addition, moreor less adjudication operations may be performed as at least part of theadjudication process.

The amount of reimbursement paid to the pharmacy by a plan sponsorand/or money paid by the member may be determined at least partiallybased on the type(s) of pharmacy network in which the pharmacy isincluded. Other factors may also be used to determine the amount inaddition to the type of pharmacy network. For example, if the memberpays the pharmacy for the prescription drug without the prescriptiondrug benefit provided by the PBM (e.g., by paying cash without use ofthe prescription drug benefit or by use of a so-called pharmacy discountcard offering other negotiated rates), the amount of money paid by themember may be different than when the member uses prescription or drugbenefit. In some embodiments, the amount of money received by thepharmacy for dispensing the prescription drug and for the prescriptiondrug itself may be higher than when the member uses the prescription ordrug benefit. Some or all of the foregoing operations may be performedby executing instructions stored on the benefit manager device 102and/or an additional device.

Examples of the network 104 include Mobile Communications (GSM) network,a code division multiple access (CDMA) network, 3^(rd) GenerationPartnership Project (3GPP), an Internet Protocol (IP) network, aWireless Application Protocol (WAP) network, a WiFi network, or an IEEE802.11 standards network, as well as various combinations thereof. Thenetwork 104 may include an optical network. The network 104 may be alocal area network or a global communication network, such as theInternet. In some embodiments, the network 104 may include a networkdedicated to prescription e-orders, e.g., a prescribing network such asthe electronic prescribing network operated by Surescripts of Arlington,Va.

Moreover, although the system shows a single network 104, multiplenetworks can be used. The multiple networks may communicate in serieswith each other to link the devices 102, 106-110 or in parallel to linkthe devices 102, 106-110.

The pharmacy device 106 may include an order processing device 114, apharmacy manager device 116, and a pharmacy fulfillment device 112 incommunication with each other directly and/or over the network 104.

The order processing device 114 may receive information regardingfilling prescriptions and may direct an order component to one or morethan one of the devices of the pharmacy fulfillment device 112 at apharmacy. The pharmacy fulfillment device 112 may fulfill, dispense,aggregate, and/or pack the order components of the prescription drugs inaccordance with one or more than one of the prescription orders directedby the order processing device 114. The order processing device 114 maybe deployed in the system 100, or may otherwise be used.

In general, the order processing device 114 is a device located withinor otherwise associated with the pharmacy to enable fulfillment of aprescription and dispensing prescription drugs by the pharmacyfulfilment device 112. In some embodiments, the order processing device114 may be an external device separate from the pharmacy and communicatewith other devices located within the pharmacy.

For example, the external order processing device 114 may communicatewith an internal order processing device 114 and/or other deviceslocated within the system 100. In some embodiments, the external orderprocessing device 114 may have limited functionality (e.g., as operatedby a patient requesting fulfillment of a prescription drug), while theinternal pharmacy order processing device 114 may have greaterfunctionality (e.g., as operated by a pharmacist).

The order processing device 114 may track the prescription order as itis fulfilled by the pharmacy fulfillment device 112. The prescriptionorder may include one or more than one prescription drugs to be filledby the pharmacy. The order processing device 114 may make pharmacyrouting decisions and/or order consolidation decisions for theparticular prescription order. The pharmacy routing decisions mayinclude what device(s) in the pharmacy are responsible for filling orotherwise handling certain portions of the prescription order. The orderconsolidation decisions include whether portions of one prescriptionorder or multiple prescription orders should be shipped together for apatient or a patient family. The order processing device 114 may alsotrack and/or schedule literature or paperwork associated with eachprescription order or multiple prescription orders that are beingshipped together.

The pharmacy management device 116 may enable and/or facilitatemanagement and operations in a pharmacy. For example, the pharmacymanagement device 116 may provide functionality to enable receipt andprocessing of prescription drug claims, management of pharmacypersonnel, management of pharmaceutical and non-pharmaceutical products,track products in the pharmacy, record workplace incidents involvepersonnel and products, and the like. In some embodiments, the orderprocessing device 114 may operate in combination with the pharmacymanagement device 116.

In some embodiments, the pharmacy management device 116 may be a deviceassociated with a retail pharmacy location (e.g., exclusive pharmacylocation, a grocery store with a retail pharmacy, or a general salesstore with a retail pharmacy) or other type of pharmacy location atwhich a member attempts to obtain a prescription. The pharmacymanagement device 116 may be utilized by the pharmacy to submit theclaim to the PBM (e.g., through the benefit management device 102) foradjudication.

In some embodiments, the pharmacy management device 116 may enableinformation exchange between the pharmacy and the PBM, for example, toallow the sharing of member information such as drug history, and thelike, that may allow the pharmacy to better service a member (e.g., byproviding more informed therapy consultation and drug interactioninformation, etc.). In some embodiments, the benefit manager 102 maytrack prescription drug fulfillment and/or other information forpatients that are not members or have not identified themselves asmembers, at the time (or in conjunction with the time) in which theyseek to have a prescription filled at a pharmacy.

The pharmacy fulfillment devices 112, the order processing device,and/or the pharmacy management device 116 may include circuitry, aprocessor, a memory to store data and instructions, and communicationfunctionality. The pharmacy management device 116 may include aplurality of processors operatively coupled to memory circuitry toexecute instructions stored in memory. These devices 112-116, in someembodiments are dedicated to performing processes, methods and/orinstructions described herein. Other types of electronic devicesspecifically configured to implement with the processes, methods and/orinstructions described herein may also be used.

In some embodiments, at least some functionality of the order processingdevice 114 may be included in the pharmacy management device 116 mayinclude circuitry, a processor, a memory to store data and instructions,and communication functionality. These devices 112-116, in someembodiments, are dedicated to performing processes, methods and/orinstructions described herein. Other types of electronic devicesspecifically configured to implement with the processes, methods and/orinstructions described herein may also be used.

In some embodiments, at least some functionality of the order processingdevice 114 may be included in the pharmacy management device 116. Theorder processing device 114 may be in a client-server relationship withthe pharmacy management device 116, in a peer-to-peer relationship withthe pharmacy management device 116, or in a different type ofrelationship with the pharmacy management device 116. The orderprocessing device 114 and/or the pharmacy management device 116 maycommunicate directly (e.g., by utilizing a local storage) and/or throughthe network 104 (e.g., by utilizing a cloud configuration or software asa service, etc.) with the storage 110.

The user device 108 is used by a device operator. The device operatormay be a user (e.g., an employee, a contractor, a benefit member, apatient of the pharmacy, or the like) associated with the system 100.Other device operators may also operate the user device 108. A deviceoperator may include other devices operated by circuitry. In someembodiments, the user device 108 may enable the device operator toattend to pharmacy operations in a convenient manner (e.g., remote froma pharmacy). In some embodiments, the user device 108 may enable thedevice operator to receive information about pharmacy processes,prescription drug fulfillment status, and the like.

The user device 108 may be a stand-alone device that solely provides atleast some of the functionality of the methods and systems, or may be amulti-use device that has functionality outside off analysis of themethods and systems. Examples of the user device 108 include a set-topbox (STB), a receiver card, a mobile telephone, a personal digitalassistant (PDA), a display device, a portable gaming unit, a computingsystem, and the like. Other devices, however, may also be used. In someembodiments, the computing system may include a mobile computing device.For example, the user device 108 may include a mobile electronic device,such as an iPhone or iPad by Apple, Inc., and mobile electronic devicespowered by Android by Google, Inc. The user device 108 may also includeother computing devices, such as desktop computing devices, notebookcomputing devices, netbook computing devices, gaming devices, and thelike. Other types of electronic devices may also be used. These devicesinclude processor circuitry that execute instructions to perform tasksas described herein.

The storage device 110 may include: a non-transitory storage (e.g.,memory, hard disk, CD-ROM, and the like) in communication with thebenefit manager device 102, the pharmacy device 106, and/or the userdevice 108 directly and/or over the network 104. The non-transitorystorage may store order data 118, member 120, claims data 122, drug data124, prescription data 126, and/or plan sponsor 128. Further, the system100 may include additional devices, which may communicate with eachother directly or over the network 104.

The order data 118 may be related to a prescription order. The orderdata may include the type of the prescription drug (e.g., drug name andstrength) and quantity of the prescription drug. The order data 118 mayalso include data used for completion of the prescription, such asprescription materials and/or the type and/or size of container in whichthe drug is dispensed or in which is requested to be dispensed. Ingeneral, prescription materials include an electronic copy ofinformation regarding the prescription drug for inclusion with orotherwise provided (e.g., via email) in conjunction with the fulfilledprescription. The prescription materials may include electronicinformation regarding drug interaction warnings, recommended usagepossible side effects, expiration date, date of prescribing, or thelike. The order data 118 may be used by the pharmacy to fulfill apharmacy order, e.g., using containers that include a machine code onthe outside of the container wall.

In some embodiments, the order data 118 includes verificationinformation associated with fulfillment of the prescription in thepharmacy. For example, the order data 118 may include videos and/orimages taken of (i) the prescription drug prior to dispensing, duringdispensing, and/or after dispensing, (ii) the prescription container(e.g., a prescription bottle and sealing lid, prescription packaging,and the like) used to contain the prescription drug prior to dispensing,during dispensing, and/or after dispensing, (iii) the packaging and/orpackaging materials used to ship or otherwise deliver the prescriptiondrug prior to dispensing, during dispensing, and/or after dispensing,and/or (iv) the fulfillment process within the pharmacy. Other types ofverification information, such as bar code data read from pallets, bins,trays, carts, and the like used to facilitate transportation ofprescriptions within the pharmacy may also be stored as order data 118.

The member data 120 includes information regarding the membersassociated with the PBM. The information stored as member data 120 mayinclude personal information, personal health information, protectedhealth information, fitness data, health data, web and mobile appactivity, and the like. Examples of the member data 120 include name,address, telephone number, e-mail address, prescription drug history,and the like. The member data 120 may include a plan sponsor identifierthat identifies the plan sponsor associated with the member and/or amember identifier that identifies the member to the plan sponsor. Themember data 120 may also include, by way of example, dispensationpreferences such as type of label, type of cap, message preferences,language preferences, or the like.

The member data 120 may be accessed by various devices in the pharmacyto obtain information utilized for fulfillment and shipping ofprescription orders. In some embodiments, an external order processingdevice 114 operated by or on behalf of a member may have access to atleast a portion of the member data 120 for review, verification, orother purposes.

In some embodiments, the member data 120 may include information forpersons who are patients of the pharmacy but are not members in apharmacy benefit plan being provided by the PBM. For example, thesepatients may obtain drugs directly from the pharmacy, through a privatelabel service offered by the pharmacy, or otherwise. In general, the useof the terms member (e.g., of a prescription drug benefit plan) andpatient (e.g., of a pharmacy) may be used interchangeably in thisdisclosure.

The claims data 122 includes information regarding pharmacy claimsadjusted by the PBM under a drug benefit program provided by the PBM forone, or more than one, plan sponsor. In general, the claims data 122includes an identification of the client that sponsors the drug benefitprogram under which the claim is made, and/or the member that purchasedthe prescription drug giving rise to the claim, the prescription drugthat was filled by the pharmacy (e.g., the national drug code number),the dispensing date, generic indicator, GPI number, medication class,the cost of the prescription drug provided under the drug benefitprogram, the copay/coinsurance amount, rebate information, and/or membereligibility, and the like. Additional information may be included.

In some embodiments, other types of claims beyond prescription drugclaims may be stored in the claims data 122. For example, medicalclaims, dental claims, wellness claims, or other types of healthcare-related claims for members may be stored as a portion of the claimsdata. The claims data 122 can include the data read from the machinereadable code on the container.

In some embodiments, the claims data 122 includes claims that identifythe members with whom the claims are associated. In some embodiments,the claims data 122 includes claims that have been de-identified (e.g.,associated with a unique identifier but not with a particular,identifiable member), aggregated, and/or otherwise processed.

The drug data 124 may include drug name (e.g., technical name and/orcommon name), other names by which the drug is known by, activeingredients, an image of the drug (e.g., in pill form), and the like.The drug data 124 may include information associated with a singlemedication or multiple medications. The drug data 124 can be informationthat is confirmed using the data read from the machine readable code onthe container.

The prescription data 126 may include information regardingprescriptions that may be issued by prescribers on behalf of patients,who may be members of the pharmacy benefit plan, for example to befilled by a pharmacy. Examples of the prescription data 126 includepatient names, medication or treatment (such as lab tests), dosinginformation, and the like. The prescriptions may be electronicprescriptions, paper prescriptions that have been scanned, or otherwise.In some embodiments, the dosing information reflects a frequency of use(e.g., once a day, twice a day, before each meal, etc.) and a durationof use (e.g., a few days, a week, a few weeks, a month, etc.).

In some embodiments, the order data 118 may be linked to associatedmember data 120, claims data 122, drug data 124, and/or prescriptiondata 126.

The plan sponsor data 128 includes information regarding the plansponsors of the PBM. Examples of the plan sponsor data 128 includecompany name, company address, contact name, contact telephone number,contact e-mail address, and the like.

FIG. 2 illustrates the pharmacy fulfillment device 112, according to anexample embodiment. The pharmacy fulfillment device 112 may be used toprocess and fulfill prescriptions and prescription orders. Afterfulfillment, the fulfilled prescriptions are packed for shipping.

The pharmacy fulfillment device 112 may include devices in communicationwith the benefit manager device, the order processing device 114, and/orthe non-transitory storage 110, directly or over the network 104.Specifically, the pharmacy fulfillment device 112 may include palletsizing and pucking device(s); loading device(s) 208; inspect device(s)210, unit of use device(s) 212, automated dispensing device(s) 214,manual fulfillment device(s) 214, review device(s) 218, imagingdevice(s) 220, cap device(s) 222, accumulation device(s) 224, literaturedevice(s) 228, packing device(s) 226, and unit of use packing device(s)230. Further, the pharmacy fulfillment device 112 may include additionaldevices, which may communicate with each other directly or over thenetwork 104.

In some embodiments, operations performed by one or more of thesedevices 206-230 may be performed sequentially, or in parallel with theoperations of devices as may be coordinated by the order processingdevice 114. In some embodiments, the order processing device 114 tracksa prescription with the pharmacy based on operations performed by one ormore than one of the devices 206-230.

In some embodiments, the pharmacy fulfillment device 112 may transportprescription drug containers, for example, between more than one of thedevices 206-230 in a high volume fulfillment center, by use of pallets.The pallet sizing and pucking device 206 may configure pucks in apallet. A pallet may be a transport structure for a number ofprescription containers, and may include a number of cavities. A puckmay be placed in one or more than one of the cavities in a pallet by thepallet sizing and pucking device 206. The puck may include a receptaclesized and shaped to receive a prescription container. Such containersmay be supported by the pucks during carriage in the pallet. Differentpucks may have differently sized and shaped receptacles to accommodatecontainers of differing sizes, as may be appropriate for differentprescriptions.

The arrangement of pucks in a pallet may be determined by the orderprocessing device 114 based on prescriptions that the order processingdevice 114 decides to launch. The arrangement logic may be implementeddirectly in the pallet sizing and pucking device 206. Once aprescription is set to be launched, a puck suitable for the appropriatesize of container for that prescription may be positioned in a pallet bya robotic arm or pickers. The pallet sizing and pucking device 206 maylaunch a pallet once pucks have been configured in the pallet.

The loading device 208 may load prescription containers into the puckson a pallet by a robotic arm, a pick and place mechanism, or the like.In one embodiment, the loading device 208 has robotic arms or pickers tograsp a prescription container and move it to and from a pallet or toand from a puck. The loading device may also print a label that isappropriate for a container that is to be loaded onto the pallet andapply the label to the container. The pallet may be located on aconveyor assembly during these operations (e.g., at the high volumefulfillment center or the like).

The inspect device 210 may verify that containers in a pallet arecorrectly labeled and in the correct spot on the pallet. The inspectdevice 210 may scan the label on one or more than one container on thepallet. Labels of containers may be scanned or imaged in full or in partby the inspect device 210. Such imaging may occur after the containerhas been lifted out of its puck by a robotic arm, picker, or the like,or may be otherwise scanned or imaged while retained in the puck. Insome embodiments, images and/or video captured by the inspect device maybe stored in the storage device as a portion of the order data 118.

The unit of use device 212 may temporarily store, monitor, label, and/ordispense unit of use products. In general, unit of use products areprescription drug products that may be delivered to a patient or memberwithout being repackaged at the pharmacy. These products may includepills in a container, pills in a blister pack, inhalers, liquids in aspray or other dispensing container, and the like. Prescription drugproducts dispensed by the unit of use device 212 may be packagedindividually or collectively for shipping, or may be shipped incombination with other prescription drugs dispensed by other devices(e.g., in the high volume fulfillment center). The unit of use productsmay include manufacturers containers.

At least some of the operations of the devices 206-230 may be directedby the other processing device 114. For example, the manual fulfillmentdevice 216, the review device 218, the automated dispensing device 214,the packing device 226, and/or another device may receive instructionsprovided by the order processing device.

The automated dispensing device 214 may include one or more than onedevice that dispenses prescription drugs or pharmaceuticals intoprescription containers in accordance with one or multiple prescriptionorders. In general, the automated dispensing device 214 may includemechanical and electronic components with, in some embodiments, softwareand/or logic to facilitate pharmaceutical dispensing that wouldotherwise be performed in a manual fashion by a pharmacist and/orpharmacist technician. For example, the automated dispensing device 214may include high volume fillers that fill a number of prescription drugtypes at a rapid rate and blister pack machines that dispense and packdrugs into a blister pack. Prescription drugs dispensed by the automateddispensing devices 214 may be packaged individually or collectively forshipping, or may be shipped in combination with other prescription drugsdispensed by other devices in the high volume fulfillment center.

The manual fulfillment device 216 may provide for manual fulfillment ofprescriptions. For example, the manual fulfillment device 216 mayreceive or obtain a container and enable fulfillment of the container bya pharmacist or pharmacy technician. In some embodiments, the manualfulfillment device 216 provides the filled container to another devicein the pharmacy fulfillment devices 112 to be joined with othercontainers in a prescription order for a patient or member. In general,a manual fulfillment may include operations at least partially performedby a pharmacist or a pharmacy technician. For example, a person mayretrieve a supply of the prescribed drug, may make an observation, maycount out a prescribed quantity of drugs and place them into aprescription container, or the like. Some portions of the manualfulfillment process may be automated by use of a machine. For example,counting of capsules, tablets, or pills may be at least partiallyautomated (e.g., through use of a pill counter or the like).Prescription drugs dispensed by the manual fulfillment device 216 may bepackaged individually or collectively for shipping or may be shipped incombination with other prescription drugs dispensed by other devices inthe high volume fulfillment center.

The review device 218 may process prescription containers to be reviewedby a pharmacist for proper pill count, exception handling, prescriptionverification, and the like. Fulfilled prescriptions may be manuallyreviewed and/or verified by a pharmacist, as may be required by state orlocal law. A pharmacist or other licensed pharmacy person who maydispense certain drugs in compliance with local and/or other laws mayoperate the review device 218 and visually inspect a prescriptioncontainer that has been filled with a prescription drug. The pharmacistmay review, verify, and/or evaluate drug quantity, drug strength, and/ordrug interaction concerns, or otherwise perform pharmacist services. Thepharmacist may also handle containers which have been flagged as anexception, such as containers with unreadable labels, containers forwhich the associated prescription order has been cancelled, containerswith defects, and the like. In an example embodiment, the manual reviewmay be performed at the manual station.

The imaging device 220 may image containers prior to filling and/orafter they have been filled with pharmaceuticals. The imaging device 220may measure a fill height of the pharmaceuticals in the container basedon the obtained image to determine if the container is filled to thecorrect height given the type of pharmaceutical and the number of pillsin the prescription. Images of the pills in the container may also beobtained to detect the size of the pills themselves and markingsthereon. The images may be transmitted to the order processing device114, and/or stored in the storage device 110 as part of the order data118.

The cap device 222 may be used to cap or otherwise seal a prescriptioncontainer. In some embodiments, the cap device 222 may secure aprescription container with a type of cap in accordance with a patientpreference (e.g., a preference regarding child resistance, a preferenceregarding built-in adherence functionality, or the like), a plan sponsorpreference, a prescriber preference, or the like. The cap device 222 mayalso etch a message into the cap or otherwise associate a message intothe cap, although this process may be performed by a different device inthe high volume fulfillment center.

The accumulation device 224 accumulates various containers ofprescription devices in a prescription order. The accumulation device224 may accumulate prescription containers from various devices or areasof the pharmacy. For example, the accumulation device 224 may accumulateprescription containers from the unit of use device 212, the automateddispensing device 214, the manual fulfillment device 216, and the reviewdevice 218, at the high volume fulfillment center. The accumulationdevice 224 may be used to group the prescription containers prior toshipment to the member or otherwise.

The literature device 228 prints, or otherwise generates, literature toinclude with prescription drug orders. The literature may be printed onmultiple sheets of substrates, such as paper, coated paper, printablepolymers, or combinations thereof. The literature printed by theliterature device 228 may include information required to accompany theprescription drugs included in a prescription order, relating toprescription drugs in the order, financial information associated withthe order (e.g., an invoice or an account statement, or the like).

In some embodiments, the literature device 228 folds or otherwiseprepares the literature for inclusion with a prescription drug order(e.g., in a shipping container or the like). In some embodiments, theliterature device 228 that prints the literature may be separate fromthe literature device that prepares the literature for inclusion with aprescription order. The packing device 226 packages a prescription orderin preparation for shipping the order. The packing device 226 may box,bag, or otherwise package the fulfilled prescription order for delivery.The packing device 226 may be a wrap seal device. A wrap seal devicedeployed as the packing device 226 may be a wrap seal device. A wrapseal device deployed as the packing device 226 may pause before anindex; during the pause, one or more bottle, envelope or literatureitems have been placed within a vacuum pocket of the wrap seal device.After any bottle, envelope, or literature items have been placed in thepocket, the wrap seal device may index; specifically, the vacuum pocketmay move forward. In an example embodiment, the forward movement isabout the length of a bag (for example, between about 16 and 20 inches).

The packing device 226 may further place inserts (e.g., literature orother papers) into the packaging received from the literature device 228or otherwise. For example, bulk prescription orders may be shipped in abox, while other prescription orders may be shipped in a bag which maybe a wrap seal bag. The packing device 226 may label the box or bag withan address and a recipient's name. The label may be printed and affixedto the bag or box, be printed directly onto the bag or box, or otherwiseassociated with the bag or box. The packing device 226 may sort the boxor bag for mailing in an efficient manner (e.g., sort by deliveryaddress, sort by zip code, or the like). The packing device 226 maylabel the box or bag with an address and a recipient's name. The labelmay be printed and affixed to the bag or box, be printed directly ontothe bag or box, or otherwise associated with the bag or box. The packingdevice 226 may sort the box or bag for mailing in an efficient manner(e.g., sort by delivery address, sort by zip code, or the like). Thepacking device 226 may include ice or temperature sensitive elements forprescriptions which are to be kept within a temperature range duringshipping in order to retain efficacy or otherwise. The ultimate packagemay then be shipped through postal mail, through a mail order deliveryservice that ships via ground and/or air (e.g., UPS®, FedEx®, or DHL®,or the like), through delivery service, through a local delivery service(e.g., a courier service), through a locker box at a shipping site(e.g., an Amazon® locker, library locker, a post office box, or thelike) or otherwise.

The unit of use packing device 230 packages a unit of use prescriptionorder in preparation for shipping the order.

The pharmacy fulfillment device 112 in FIG. 2 may include single devices206-230 or multiple devices 206-230 (e.g., depending upon implementationin a pharmacy). The devices 206-230 may be the same type or model ofdevice or may be different device types or models. When multiple devicesare present, the multiple devices may be of the same device type ormodels or may be a different device type or model. The types of devices206-230 shown in FIG. 2 are example devices. In other configurations ofthe system 100, lesser, additional, or different types of devices may beincluded.

Moreover, multiple devices may share processing and/or memory resources.The devices 206-230 may be located in the same area or in differentlocations. For example, the devices 206-230 may be located in a buildingor a set of adjoining buildings. The devices 206-230 may beinterconnected (e.g., by conveyors), networked, and/or otherwise incontact with one another or integrated with one another (e.g., at thehigh volume fulfillment center). In addition, the functionality of adevice may be split among a number of discrete devices and/or combinedwith other devices.

FIG. 3 is a schematic view illustrating an exemplary embodiment of theunit of use device 212 for storing, monitoring, and labeling prepackagedprescription drug containers, namely, prepackaged medication bottles320. In an example embodiment, the unit of use device 212 can operate onmanufacturer containers. As discussed in further detail below, inoperation, the unit of use device 212 receives instructions from theorder processing device 114. Upon receipt of instructions, the unit ofuse device 212 handles and verifies the contents a medication bottle 320and delivers the bottle 320 to the packing device 224 via a conveyorchute 322. Alternately, if the unit of use device 212 cannot verify thecontents of the bottle 320 or the contents of the bottle 320 does notmatch the instructions from the order processing device 114, then theunit of use device 212 delivers the bottle to a discharge bin 324. Thebottles 320 may contain any suitable types of medications including, forexample, liquid medications, pills, capsules, etc.

The medication bottles 320 a-h in the bottle area are arranged in aplurality of rows with each row containing a plurality of identicalbottles and with at least some of the different rows containingdifferent types of bottles 320 a-h and/or similar bottles with differentcontents. For example, the bottles 320 a-h in the different rows mayhave different shapes (e.g., a cylindrical shape or a rectangularparallelepiped shape) and/or sizes from one another. In an embodiment,the bottles 30 a-h can range in size from one to nine inches (1-9 in) indiameter or width. In an embodiment, the rows are angled downwardly in adirection towards a robotic arm 326 (discussed in further detail below)so that when a bottle 320 a-h is removed from the bottle area by therobotic arm 328, the other bottles 320 a-h automatically slide downwardtowards the robotic arm 326 such that a next bottle 320 a-h is in aready to pick position for the robotic arm 326. The bottles 320 a-h canthus be restocked into the various rows from an opposite side of thebottle area from the robotic arm 326. This allows the bottle area to berestocked (either automatically or manually) without interrupting theoperation of the robotic arm 326 or the other components of the unit ofuse device 212. The bottles 320 a-h can be labeled with a machinereadable code, which can be positioned differently from container tocontainer of a same type or be positioned differently on different typesof containers. Moreover, the bottles 320 a-h can be of differentdimensions, e.g., outer perimeter, circumference or the like, such thatthe machine code extends around a different percentage of the outerdimension of the bottle.

As shown in FIGS. 4A and 4B, each bottle 320 a, 320 b has a cup portion330 a, 330 b and a removable cap 332 a, 332 b. A first label 334 a, 334b, which contains an optical machine-readable code, is adhered to thecup portion 330 a, 330 b prior to the bottle 320 a, 320 b being stockedinto the bottle area. In the exemplary embodiment, the machine readablecodes are barcodes. However, it should be appreciated that Quick Read(QR) codes or any suitable types of machine readable codes which can beread with an optical sensor, such as a camera, could alternately beemployed. The machine readable code contains information on the contentsof the bottle 320 a, 320 b, e.g., the type and quantity of themedication contained in the bottle 320 a, 320 b. In an exampleembodiment, the machine readable code is a bar code, numerical code orthe like.

Referring back to FIG. 3, the unit of use device 212 includes acontroller 328 which electronically receives the instructions from theorder processing device 114. In operation, the controller 328 instructsthe robotic arm 326 (or another pick and place mechanism) on which oneof the bottles 320 a-h in the bottle area to pick up and where todeliver it.

Referring now to both FIGS. 3 and 4, in the exemplary embodiment, therobotic arm 326 is a six-axis robotic arm 326 that has a grippingmechanism 336 which is able to releasably engage with the caps 332 ofthe bottles 320 in the bottle area and lift the bottles by the caps 332.Once the bottle 320 has been lifted, the robotic arm 326 is configuredto the bottle 320 to one of two imaging systems 338. As discussed infurther detail below, each imaging system 338 is configured to read themachine readable code on the first label 334 to verify the bottle whichhas been picked by the robotic arm 326 matches the instructions receivedby the controller 328. In the exemplary embodiment, the unit of usedevice 212 includes two similarly constructed imaging systems so thatthe robotic arm 326 can bring the picked up bottle 320 to whicheverimaging system is nearest. Thus, in the arrangement shown in FIG. 3,bottles 320 a-d will all be brought to one imaging system 338 andbottles 320 e-h will all be brought to the other imaging system 338.This configuration saves time by reducing the distance that any givenbottle 320 has to travel from the bottle area to the imaging system 338and allows the unit of use device 212 to operate more quickly. In otherembodiments, the unit of use device 212 has only a single imaging system338 or three or more imaging systems 338.

Adjacent each of the imaging systems 338, the unit of use device 212includes a label applicator 340. When the imaging system 338 confirmsthat the contents of a bottle 320 matches the contents which was orderedby the order processing device 114, the label applicator prints out anew second label, and the robotic arm 326 moves the bottle 320 from theimaging system 338 to the label applicator 340 to apply the second labelover the first label 334. The second label may include, for example, apatient's name, the type of medication contained in the bottle 320, thequantity of medication contained in the bottle 320, prescriptioninstructions, an expiration date, etc.

Referring now to FIGS. 3, 4A, and 4B, in the exemplary embodiment, eachimaging system 338 includes a camera system which includes a pluralityof cameras 342 that can each identify the optical machine-readable code.In other embodiments, the imaging system 338 may contain barcodescanners or the like. The cameras 342 are all mounted in such a way thatthey are spaced apart from one another and face towards a central axis Aso that when one of the bottles 320 a, 320 b brought by the robotic arm326 into a space along the central axis A, the cameras 342 can scan forthe machine readable code on the first label 334 a, 334 b. If any one ofthe cameras 342 is able to detect and read the machine readable code,then a signal is sent from the imaging system 338 to the controller 328.The controller 328 compares the bottle 320 a, 320 b to the bottle thatwas requested by the order processing device 114. The cameras 342 may bein electronic communication with a memory (not shown) which canelectronically store any images taken by the cameras 342 duringoperation of the unit of use device 212. In some cases (such as FIG.4B), more than one of the cameras 342 may combine to detect and read themachine readable code.

If none of the cameras 342 is able to detect and read the machinereadable code on the first label 334 a, 334 b, then the imaging system338 is able to reorient the cameras 342 to scan the bottle 320 a, 320 bfrom different vantage points. To reorient the cameras 342, in theexemplary embodiment, the imaging system 338 includes a rotationalelement in the form of a rotating plate 344 which is circular in shapearound the central axis A. The rotating plate 344 supports the cameras342 in such a manner that the lenses 346 of all of the cameras 342 allface towards the central axis A. The rotating plate 344 is preferablymade out of a rigid material, e.g., a metal, such as steel, a steelalloy, or an aluminum alloy. However, any suitable material may beemployed. In other embodiments, the rotating plate 344 has anon-circular shape.

A plurality of cylindrically shaped camera mount rods 348 are equallyspaced apart from one another and are fixedly attached with the rotatingplate 344 adjacent an outer perimeter of the rotating plate 344. In theexemplary embodiment, fasteners (such as bolts) extend through the mainplate 344 and engage the camera mount rods 348 to fixedly attach thesecomponents together. In other embodiments, the camera mount rods 348 arefixedly attached with the rotating plate 344 via other attachment means,such as welding.

The camera mount rods 348 all extend in parallel relationship with oneanother and with the central axis A. As shown in FIG. 7, the rotatingplate 344 is fixedly attached with a rotation shaft 350 which is itselfsupported by a bearing 352 to allow the rotating plate 344 to rotate andadjust the positions of the cameras 342 around the central axis A. Therotation shaft 350 has a first end face which is fixedly attached withone side face of the rotating plate 344 along the central axis A via apair of fasteners 354 which extend through the rotating plate 344 andare in a threaded engagement with a pair of threaded blind holes formedinto the rotation shaft 350.

The rotation shaft 350 extends along the central axis A through thebearing 352 to a second end face on an opposite side of the bearing 352from the rotating plate 344. The rotation shaft 350 has a retaining ringgroove which receives a retaining ring 356 adjacent the second end facefor holding the rotation shaft 350 on the bearing 352. A pair of flangedbushings are partially inserted into a radial gap between an outersurface of the rotation shaft 350 and an inner race of the bearing 352.

The bearing 352 is supported by a bearing mount 357 that is attachedwith a fixed surface, such as a wall. In the exemplary embodiment, thebearing 352 is a roller bearing. However, other types of bearings mayalternately be employed, including ball bearings.

Referring now to FIG. 8, each camera 342 is fixedly attached with an endof its respective camera mount rod 348 via a mounting fixture 358 whichincludes a base plate 360, an L-bracket 362, and a clamp 364. Aplurality of fasteners extend through the base plate 360 to threadedlyengage with the camera 342 and thereby fixedly attach the camera 342with the base plate 360. The L-bracket 362 has a first leg that isfixedly attached with the base plate 360 and a second leg that isfixedly attached with the clamp 364. The clamp 364 has an opening whichreceives the respective camera mount rod 348. The clamp 364 furtherincludes a slot 366 which extends from a side of the clamp 364 to theopening. A clamp fastener 368, such as a set screw, extends across theslot 366 and is threadedly engaged with the clamp 364 for tightening theclamp 364 onto the respective camera mount rod 348. This configurationof the mounting fixture 348 allows both the axial location and theorientation of the camera along the camera mount rod 348 to be preciselychosen and adjusted by simply loosening the clamp fastener 368, makingthe necessary adjustments, and re-tightening the clamp fastener 368.

Referring back to FIGS. 4A and 4B, each camera 342 has a lens 346 whichfaces towards the central axis for viewing the bottle 320 that is beingheld stationary by the robotic arm 326. Each camera 342 also has a lightsource 370 (shown in FIG. 8), which is preferably a light emitting diode(LED), that is directed generally towards the central axis, i.e., in thesame direction as the lens 346. On an opposite side of the camera 342from the lens 346 and the light source 370, each camera 342 has a powerport 372 which receives a power cord (not shown) and an communicationport 374 which receives a communication cord (not shown) which enablesthe camera 342 to communicate with the controller 328 (shown in FIG. 3).In an example, the communication port includes an ethernet port, serialport or the like to receive a communication cord. In other embodiments,the camera 342 may be powered by an internal power source, such as abattery, and may communicate with the controller 328 through othercommunication means which may be either wired (e.g., bus) or wireless(e.g., Bluetooth, NFC, WiFi, cellular, or the like.

The imaging system 338 further includes an actuator 376 for rotating therotating plate 344, along with the cameras 342, around the central axisand any bottle 320 being held stationary in the imaging system 338 bythe robotic arm 326 to give the cameras 342 different vantage points onthe bottle 320 if none of the cameras 342 are able to initially findand/or read the machine readable code after a first scan is completed.That is, the bottle 320 is held radially inwardly from the camera lenseswithin the field of view of at least cameras but not in contact withcameras or plate. A robotic arm extends toward the plate to place thebottle in the field of view of the cameras. The cameras are pointedinwardly generally toward the rotational axis of the plate. However, therobotic arm and the bottle do not mechanically contact the plate,cameras or the camera brackets. The actuator 376 is pivotably mounted toan actuator bracket 378 and has an actuator rod 380 and a housing 382,and activation of the actuator 376 by the controller 328 causes theactuator rod 380 to extend into or out of the housing 382. An end of theactuator rod 380 has a pivotable eye hole, and a fastener extendsthrough an opening in the rotating plate 344 and through the eye hole tooperably attach the rotating plate 344 with the actuator 376. Thus,activation of the actuator 376 causes the rotating plate 344 and thecameras 342 to rotate about the central axis from respective firstpositions (shown in FIG. 5) to respective second positions (shown inFIG. 6). When the actuator rod 380 travels in one direction (into or outof the housing 382), the rotating plate 344 and cameras 342 rotate inone direction (clockwise or counter-clockwise), and when the actuatorrod 380 travels in an opposite direction (into or out of the housing382), the rotating plate 344 and cameras 342 rotate in an oppositedirection (clockwise or counter-clockwise).

In the exemplary embodiment, the actuator 376 is configured such thatthe rotation from the first positions to the second positions isapproximately thirty degrees (30°). In other embodiments, the first andsecond positions may be either greater or less than thirty degrees (30°)from one another. In the exemplary embodiment, the actuator 376 is apneumatic linear actuator. In other embodiments, the actuator 376 may behydraulically or electrically powered and may be non-linear.

Operation of the unit of use device 212 is as follows with reference tothe flow chart of FIG. 9 and the structure shown in FIGS. 3-8. At step900, instructions are received by the controller 328 from the orderprocessing device 114. At step 902, the controller 328 processes theinstruction and directs the robotic arm 326 to pick up a specific typeof bottle 320 a-h from the bottle area according to the instructions andtransport the bottle 320 to the imaging system 338, which can be thenearest imaging system. At step 904, the robotic arm 326 holds thebottle 320 in a position along the central axis and between the cameras342. In an example embodiment, the robotic arm 326 holds the cap end ofthe bottle 320 with the closed bottom end adjacent the plate 344 whilenot mechanically contacting the cameras or the plate 344. At step 906,the controller 328 then temporarily activates the cameras 342 to performa first scan for the machine readable code on the bottle 320. Atdecision step 908, the controller 328 determines whether the machinereadable code was successfully found and read from any of the imagestaken by the cameras 342.

If the answer at step 908 is yes, then the process proceeds to decisionstep 910. At step 910, the controller 328 determines whether the machinereadable code is the correct machine readable code which aligns with theinstructions received from the order processing device 114 in step 900.If the answer to step 910 is yes, then at step 912, the robotic arm 328carries the bottle 320 to the label applicator 340, which automaticallyprints and applies a new, second label to the bottle 320 on top of thefirst label 334. Next, at step 914, the robotic arm 326 drops the bottle320 into the conveyor chute 322, which carries the bottle 320 to thepacking device 226.

If the answer to step 910 is no, then at step 916, the robotic arm 326drops the bottle 320 into the discharge bin 324.

If the answer to step 908 is no, then the process proceeds to step 918.At step 918, the controller 328 activates the actuator 376 to rotate therotating plate 344 and the cameras 342 around the central axis fromrespective first positions (shown in FIG. 5) to respective secondpositions (shown in FIG. 6). In the second positions, the cameras 342have different vantage points than they did in their respective firstpositions. Thus, in many cases where the machine readable code was notin the vantage fields any of the cameras 342 when the cameras were inthe first positions, it may now be in the vantage field of one of thecameras 342 in the second positions. At step 920, the cameras 342 aretemporarily re-activated to perform a second scan of the bottle 320 forthe machine readable code. At step 922, the controller 328 activates theactuator 376 to rotate the rotating plate 344 and the cameras 342 in anopposite direction from step 918 back to their respective firstpositions.

The process then proceeds to decision step 924. At step 924, thecontroller 328 determines whether the machine readable code wassuccessfully read from the images taken by the cameras 342 during thesecond scan. If the answer to step 924 is yes, then the method proceedsto aforementioned decision step 910. If the answer to step 924 is no,then the process proceeds to aforementioned step 916.

In an example embodiment, the machine readable code extends around thebottle such that the code is not readable by a single camera. At least aportion of the machine readable code extends around the container ontoanother wall of the container such that a single camera cannot read themachine readable code. In an example, the machine readable codedisappears over the horizon in the image taken by the camera.

In an example embodiment, the cameras have a field of view in thehorizontal direction and the vertical direction. The plate turns torotate the cameras if the entire machine readable code is not in thefield of view of a single camera cannot read the machine readable code.In another example embodiment, the robotic arm rotates the bottle in adirection counter to the rotation of the plate.

In an example embodiment, the robotic arm holds the container co-linearwith the rotational axis of the plate and/or the cameras. In otherembodiment, the robotic arm holds the container within the field ofviews of the cameras but is not positioned co-linear with the rotationalaxis.

The present disclosure uses the term bottle and the term container. Acontainer can be an object to store or transport contents. A bottle isalso an object to store content, which can have a narrower neck. Theseterms can be used in the present described systems and processes as bothcan store pharmaceuticals, medicines, supplements and the like. In thepresent system, the bottles and containers store contents that should beverified using the cameras as described herein. A container can be usedin the embodiments that describe a bottle and vise versa.

Obviously, many modifications and variations of the present inventionare possible in light of the above teachings and may be practicedotherwise than as specifically described while within the scope of theappended claims. Additionally, it is to be understood that all featuresof all claims and all embodiments can be combined with each other aslong as they do not contradict each other.

What is claimed is:
 1. An imaging system for identifying medicationcontainers, comprising: a rotating element which is configured to rotateabout a central axis; a plurality of scanners fixedly attached to saidrotating element, said scanners each having a lens which faces generallytowards said central axis, and said scanners being spaced apart from oneanother around said central axis; said scanners being configured toidentify an optically readable machine readable code contained on amedication container; and an actuator operably connected with saidrotating element and being configured to rotate said rotating elementand said scanners around said central axis from respective firstpositions to respective second positions to allow said scanners to imagedifferent areas of the medication container in response to a failure ofsaid scanners to identify the machine readable code when said scannerswere in said respective first positions.
 2. The imaging system as setforth in claim 1, wherein said scanners are cameras.
 3. The imagingsystem as set forth in claim 1, wherein said plurality of scannersincludes four scanners which are equidistantly spaced apart from oneanother around said central axis.
 4. The imaging system as set forth inclaim 1, wherein said actuator is a linear actuator.
 5. The imagingsystem as set forth in claim 1 wherein said respective second positionsof said scanners are no greater than thirty degrees (30°) from saidrespective first positions of said scanners.
 6. The imaging system asset forth in claim 1, wherein said scanners are cameras, and whereinsaid rotating element includes a circular plate and a plurality ofcamera mount rods which interconnect said cameras to said rotatingelement.
 7. The imaging system as set forth in claim 6, furtherincluding a plurality of clamps and wherein each clamp attaches one ofsaid cameras to one of said camera mount rods.
 8. A container handlingand verification system, comprising: a container area for storing atleast two different types of medication containers, the medicationcontainers having an optically readable machine readable code; a pickand place mechanism configured to engage a first medication containerand deliver the first medication container to a location along a centralaxis of an imaging system; said imaging system including a plurality ofimaging devices which face towards said central axis, and said imagingsystem including an actuator which is configured to rotate said imagingdevices about said central axis; said imaging devices being configuredto perform a first scan on the label of the first medication containerwith said imaging devices for said machine readable code; and inresponse to said imaging devices not detecting said machine readablecode on said label of said first medication container, said imageprocessing system being configured to activate said actuator to rotatesaid imaging devices about said central axis and perform a second scanon said label of said first medication container.
 9. The containerhandling and verification system as set forth in claim 8, wherein saidimaging devices are cameras.
 10. The container handling and verificationsystem as set forth in claim 8, further including a controller which isin electrical communication with said pick and place mechanism and saidimaging devices and said actuator and which controls said pick and placemechanism, said imaging devices, and said actuator upon receiving of anorder for a medication container.
 11. The container handling andverification system as set forth in claim 8 further including a conveyorchute and wherein said pick and place mechanism is configured to dropsaid first medication container in a discharge bin in response to eitherno detection of said machine readable code during both said first andsecond scans or in response to said machine readable code not matchingan expected machine readable code based upon the order received by saidcontroller.
 12. The container handling and verification system as setforth in claim 8, further including a label applicator for applying anew label to said first medication container.
 13. A method of verifyingcontents of a medication container which has an optically readablemachine readable code, comprising the steps of: holding the medicationcontainer in a stationary position such that a plurality of imagingdevices are facing the medication container; conducting a first visualscan of the medication container with the imaging devices for themachine readable code; and in response to the imaging devices notdetecting the machine readable code, rotating the imaging devices aroundthe medication container and then conducting a second visual scan of themedication container with the imaging devices for the machine readablecode with the imaging devices being at a different angle.
 14. The methodas set forth in claim 13, further comprising the steps of: receivingwith a controller an order for a medication container; and picking up afirst medication container of a plurality of different types ofmedication containers with a pick and place mechanism.
 15. The method asset forth in claim 14, further comprising the step of: in response toone of the imaging devices reading the machine readable code duringeither the first visual scan or the second visual scan, then; if themachine readable code matches an expected machine readable code based onthe order, placing the medication container in a first location usingthe pick and place mechanism, and if the machine readable code does notmatch an expected machine readable code based on the order, placing themedication container in a second location that is different than thefirst location using the pick and place mechanism.
 16. The method as setforth in claim 15, further including the step of applying a label to themedication container prior to placing the medication container in thefirst location.
 17. The method as set forth in claim 15, wherein thefirst location is a conveyor and wherein the second location is adischarge bin.
 18. The method as set forth in claim 13, wherein theimaging devices are fixedly attached to a rotating element and furtherincluding an actuator which is configured to rotate the rotating elementand the cameras.
 19. The method as set forth in claim 18, the actuatoris a linear actuator.
 20. The method as set forth in claim 19, whereinthe actuator is pneumatic.